It wouldn't have been that bad, except he was using excel. *sigh*
Here's what we've learnt so far:
- If you're making a "less than" comparison, and the cell you're checking is empty, it'll assume it's zero.
- Under VB, the operator "&" can be used as a boolean AND when it's a simple statement (e.g. (TRUE)&(FALSE) will give you FALSE), but not when it's more complicated. (e.g. ((TRUE)&(FALSE))&((TRUE)&(TRUE)) gives you "FALSETRUE". I kid you not.)
- Has anyone written a program to transform the psuedo base-26 column assignment to numbers yet?
- Nested IF-statement, or just an IF-statment with a lot of ELSE IFs, are very very VERY evil to code in excel
Honestly, I haven't been THIS frustrated for a long time. Although it does bring back some memories. Ah... thold undergrad days.
At least it's all done. We can ALL have a merry christmas, in 10 days time! :)
1 comment:
Yeah, the undergraduate days, remember the robotic project? *GOOD* old days indeed.
Post a Comment